Techniques for determining vicinity information for access points using location assistance data

ABSTRACT

Techniques are described for providing assistance data corresponding to a plurality of access points (APs). The techniques include, in part, providing assistance data to a mobile device. The assistance data comprises group data that is common among the plurality of APs. The group data is associated with a group identifier (ID). The techniques further include providing the group ID and a set of AP-specific information for at least one of the plurality of APs. The group data may include information corresponding to a common grid, common location area and/or common characteristics of the APs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a divisional application of U.S. patent applicationSer. No. 14/476,546, entitled “Techniques for Determining CommonCharacteristics of Groups of Wireless Access Points,” filed Sep. 3,2014, which claims the benefit of U.S. Provisional Application No.61/879,092 entitled “Methods of Compressing and Aligning WiFi RF HeatMaps,” filed Sep. 17, 2013, which are assigned to the assignee of thepresent application and are hereby expressly incorporated by referencein their entireties.

TECHNICAL FIELD

The present disclosure relates generally to determining a location of amobile device, and in particular, to storing and transferring radiofrequency (RF) heat maps and other information corresponding to anaccess point or base station.

BACKGROUND

Generally, a location of a mobile device (e.g., location fix) may bedetermined using measurements made by the device of radio signalstransmitted by a number of access points, base stations and/ornavigation satellites situated at known locations. Obtaining a locationfix for a mobile device has become a critically important function inrecent years. For mobile devices, there are numerous applications andweb based services that take advantage of the location fix of the mobiledevice. For example, a map application on a mobile device or on a remoteweb server can select appropriate maps, direction, driving routes, etc.,based on the current location of the mobile device. A social networkingapplication can identify other users within the vicinity based on thelocation of the mobile device. In an emergency situation, public safetycan be dispatched to the precise location of the user of a mobile deviceeven when the user is not aware of the precise location or not able tocommunicate it. Many other examples exist.

Different techniques for obtaining a position fix, also known as alocation estimate, a location or a location fix, for a mobile device maybe appropriate under different conditions. In an outdoor environment,satellite-based approaches, e.g., GNSS (Global Navigation SatelliteSystem) techniques may be suitable, because the mobile device may beable to receive satellite-based positioning signals with specific timingcharacteristics. Based on reception of such satellites signals fortypically four or more satellites, a position fix for the mobile devicemay be calculated. However, satellite-based approaches are not preferredin indoor environments, because satellite signals cannot always bereceived or accurately measured indoors.

In indoor environments, such as a shopping mall, airport, sports arena,convention center, museum, hospital, office building, etc.,terrestrial-based approaches making use of signals transmitted fromcellular base stations (BSs) and/or wireless local area network (WLAN)access points (APs) are generally more useful for obtaining an accuratelocation fix for a mobile device. The mobile device observes andmeasures signals sent from BSs and/or APs. Different types ofmeasurements may be obtained by a mobile device such as RSSI (ReceivedSignal Strength Indication) and RTT (Round-trip Time). Such measurementsmay allow the mobile device or a separate location server to estimatethe distance of the mobile device to each BS and/or AP. The mobiledevice or a location server may then estimate the location of the mobiledevice, based on the distances to different BSs and/or APs and the knownlocations of the BSs and/or APs.

In another example, the mobile device may compare the measured signalstrength from each BS or AP to a grid of signal strength data providingthe expected (e.g., calculated or previously measured) signal strengthfrom each BS or AP at different locations. The mobile device may thendetermine its location, using a process such as pattern matching, byfinding a particular location for which the expected signal strengthsfor a number of BSs and/or APs most closely match the signal strengthsmeasured by the mobile device. An advantage of this approach is that thelocations of the BSs and/or APs may not need to be known—just thelocations where signals from the BSs and/or APs can be received withdifferent expected signal strengths.

One problem with BS and/or AP-based approaches, in which patternmatching is used and in which the mobile device computes its ownlocation, is the amount of data that the mobile device may need toreceive (e.g., from an external location server) about each AP or BSwhen expected BS or AP signal strength values are provided for a largenumber of different locations. For example, a WLAN AP based on IEEE802.11 WiFi standards or a small BS (e.g., a Femto cell or Home BaseStation) may typically provide coverage up to a distance of 100 metersfrom the AP or BS, and a location service provider may wish to enablelocation accuracy with an error about one meter. In such a case,expected signal strength values may be provided in the form of a “heatmap” for a grid of location points spaced 1 meter apart from each otherover the entire AP or BS coverage area. In this example, the number ofseparate location grid points may be around 40,000 (e.g., for a squaregrid of size 200 by 200 meters centered on the AP or BS). If theexpected signal strength value for, and the location of, each grid pointcan be encoded using N octets of data, sending a heat map comprising thesignal strength data to a mobile device for the entire AP or BS coveragearea would consume 40,000×N octets. Since a mobile device may be incoverage from other APs and/or small BSs, an equivalent amount of datamay also need to be sent to the mobile device for each one of the otherAPs and/or small BSs. The total amount of data may easily be counted inmega-octets (e.g., even if N is as small as one octet) which may consumeexcessive resources in the mobile device, network and location serverfor signaling, processing and storage. In particular, this creates aproblem for the mobile device, which generally has limited processing,battery power, and memory resources.

A second problem with BS and/or AP-based location approaches is thatother data associated with BSs and APs may need to be provided to amobile device (e.g., by a location server) in addition to or instead ofa heat map for each BS and/or AP. Such other data may compriseinformation concerning the coverage area of each AP or BS (e.g., thegeographic boundary of the coverage area), the type of coverage area(e.g., whether indoors, outdoors or partly indoors and partly outdoors)and other characteristics of each AP or BS such as the manufacturer ofthe BS or AP or the type of BS or AP (e.g., whether conforming to IEEE802.11 WiFi standards or Bluetooth®). Such other data may also consumesignificant signaling, processing and storage if not transferred to amobile device in an efficient compact form. Moreover, such additionaldata may require configuration in a network server (e.g., a locationserver) which may lead to an excessive amount of operator time toperform the configuration which in turn may cause various configurationerrors when the data is configured for each of a large number of APsand/or BSs.

SUMMARY

As used herein, the term “access point” (AP) includes any wirelesscommunication station and/or device, typically installed at a fixedterrestrial location and used to facilitate communication in a wirelesscommunications system. For example, an access point may comprise awireless local area network (WLAN) access point supporting the IEEE802.11 standards or Bluetooth, a cellular base station, Macro cell basestation, Macro base station, Pico cell base station, Pico base station,Femto cell, Femto base station, eNode B, Node B, home NodeB, Home eNodeB, small cell base station or the like.

In one example, a method for providing assistance data corresponding toa first plurality of APs is disclosed. The method includes, in part,providing first assistance data to a mobile device, and providing thefirst group ID and a set of AP-specific information for at least one ofthe first plurality of APs. The first assistance data comprises a firstgroup data that is common among the first plurality of APs, the firstgroup data being associated with a first group identifier (ID). In oneexample, the first group data includes information corresponding to acommon location area for the first plurality of APs.

The first group data may also include one or more of an indication ofwhether an altitude change is allowed within the common location area, aversion, a validity period, and one or more common properties of APsincluding an identification of at least one of an AP manufacturer, an APmodel, a chip manufacturer, a chip model and a signaling type.

In another example, the first group data includes informationcorresponding to a reference grid. The reference grid may be used indetermining the set of AP-specific information. In one example, thereference grid includes at least one of a common grid point spacing,common grid origin, and a common grid orientation.

In one example, the method further includes determining the first groupdata by analyzing one or more characteristics of the first plurality ofAPs. In another example, the method further includes providing secondassistance data to the mobile device corresponding to a second pluralityof APs, and providing the second group ID. The second assistance datacomprises group data that is common among the second plurality of APs.The group data is associated with a second group ID, and the secondplurality of APs include at least one of the APs in the first pluralityof APs. In one example, at least one of the APs in the first pluralityof APs is different from at least one of the APs in the second pluralityof APs. In another example, the first assistance data is different fromthe second assistance data.

In one example, a method for obtaining assistance data corresponding toa plurality of access points is disclosed. The method includes, in part,receiving assistance data from a device, receiving the group ID and aset of AP-specific information for at least one AP among the pluralityof APs, and determining AP vicinity information corresponding to the atleast one AP based on the group ID and the set of AP-specificinformation. The assistance data includes group data that is commonamong the plurality of APs. The group data is associated with a groupID.

In one example, the group data includes information corresponding to acommon location area for the plurality of APs. In another example, thegroup data includes an indication of whether an altitude change isallowed within the common location area. In yet another example, thegroup data includes information corresponding to a reference grid thatis used in determining AP-specific information corresponding to each ofthe plurality of APs.

In one example, an apparatus for providing assistance data correspondingto a first plurality of APs is disclosed. The apparatus includes, inpart, means for providing first assistance data to a mobile device, andmeans for providing the first group ID and a set of AP-specificinformation for at least one of the first plurality of APs. The firstassistance data includes a first group data that is common among thefirst plurality of APs. The first group data is associated with a firstgroup ID.

In one example, a non-transitory computer readable medium for providingassistance data corresponding to a first plurality of APs is disclosed.The computer readable medium includes computer-readable instructionsconfigured to cause a processor to provide first assistance data to amobile device, and provide the first group ID and a set of AP-specificinformation for at least one of the first plurality of APs. The firstassistance data includes a first group data that is common among thefirst plurality of APs, the first group data being associated with afirst group ID.

BRIEF DESCRIPTION OF THE DRAWINGS

An understanding of the nature and advantages of various embodiments maybe realized by reference to the following figures. In the appendedfigures, similar components or features may have the same referencelabel. Further, various components of the same type may be distinguishedby following the reference label by a dash and a second label thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

FIG. 1 illustrates a wireless communication network, in accordance withcertain embodiments of the present disclosure.

FIG. 2 illustrates an example bounding box that can be defined within oraround a building, in accordance with certain embodiments of the presentdisclosure.

FIG. 3 illustrates an example set of grid points, in accordance withcertain embodiments of the present disclosure.

FIG. 4 illustrates an example scanning order for reading datacorresponding to a set of grid points.

FIG. 5 illustrates two example APs with their corresponding heat maps,and a mobile device, in accordance with certain embodiments of thepresent disclosure.

FIG. 6 illustrates an example common reference grid that may be used toprovide heat map information corresponding to two or more APs, inaccordance with certain embodiments of the present disclosure.

FIG. 7 illustrates several types of group data for an example set ofAPs, in accordance with certain embodiments of the present disclosure.

FIG. 8 illustrates example operations that may be performed by a deviceto provide assistance data corresponding to two or more APs, inaccordance with certain embodiments of the present disclosure.

FIG. 9 illustrates example operations that may be performed by a mobiledevice to obtain assistance data corresponding to a plurality of APs.

FIG. 10 describes one potential implementation of a device which may beused to provide and/or utilize vicinity information, according tocertain embodiments.

DETAILED DESCRIPTION

This invention provides a method for efficiently providing vicinityrelated information (e.g., RF signal strength values, location area datafor an AP coverage area, AP coverage area type) and othercharacteristics (e.g., type and manufacturer of an AP) for one or moreof a plurality of access points (APs). The vicinity information maygenerally relate to any information that is indicative of a position foreach of a plurality of locations (e.g., grid points) relative to aparticular AP. For example, the vicinity information may include signalstrength information (e.g., RSSI) at each location or grid point, timingvalues (e.g., RTT) at each location or grid point, or any other datathat can be calculated and/or measured for a location or grid point. Thevicinity information may be in the form of mean values, standarddeviation values or other statistics.

As used herein, the terms “user equipment” (UE) or “mobile device” maybe used interchangeably to refer to a device that may from time to timehave a position location that changes. For example, a mobile device maycomprise a cellular telephone, smartphone, tablet, wirelesscommunication device, mobile station, laptop computer, a personalcommunication system (PCS) device, Secure User Plane Solution (SUPL)Enabled Terminal (SET), personal digital assistant (PDA), personal audiodevice (PAD), portable navigational device, and/or other portablecommunication devices.

In one embodiment, the vicinity information for one or more APs may beused in obtaining a location fix for a mobile device in an indoorenvironment. In this embodiment, the location fix may be a positionderived from measurements made by the mobile device of signalstransmitted by APs at known or unknown locations.

Generally, vicinity information for an AP (also referred to as an RFheat map, or a heat map) is a graphical representation of data where theindividual RF signal characteristics (e.g., mean RSSI, mean RTT) arecontained in a matrix corresponding to a set of grid points. Thevicinity information for an AP may be depicted with a set of colors(e.g., where the magnitude of a signal characteristic at any grid pointdetermines a specific color around that grid point), or a set ofnumbers.

Vicinity information for an AP may also comprise a description ordefinition of a location area that contains all or part of the coveragearea of the AP. A location area may be defined geographically in termsof a circle (e.g., with given center and radius), an ellipse (e.g., withgiven center, major and minor axis and orientation), a polygon or someother geometric shape. Alternatively, a location area may be defined incivic terms—e.g., by providing an address or name for a building orbuilding complex together with an identification for a particular partof the building or building complex (e.g., such as “Terminal 4” for anairport or “Main Building, floor 5, west side” for a hospital ormuseum).

Other information that may be provided for an AP may compriseinformation about the AP manufacturer, AP model, AP capabilities (e.g.,whether supporting IEEE 802.11 signaling, Bluetooth signaling and/orsignaling associated with a particular type of cellular network).

FIG. 1 illustrates a wireless communication system 100, in accordancewith certain embodiments of the present disclosure. As illustrated, thesystem 100 may include a plurality of access points (e.g., AP1 102, AP2104, AP3 106) and user equipments (e.g., UE1 108, UE2, UE3). Inaddition, the system 100 may include a location server (LS) 110. In someembodiments, the APs 102, 104 and 106 and the LS 110 may be connected toor may be part of a wireless network 120 which may providecommunications services to UEs (e.g., UE1, UE2 and UE3) such as transferof voice and/or data between each UE and some other device. Wirelessnetwork 120 and its APs (e.g., APs 102, 104 and 106) may supportwireless communication (e.g., to and from UE1, UE2 and UE3) using anystandard or proprietary wireless technology such as Global System forMobile Communications (GSM) defined by the Third Generation PartnershipProject (3GPP), Wideband Code Division Multiple Access (WCDMA) definedby 3GPP, Long Term Evolution (LTE) defined by 3GPP, cdma2000 defined bythe Third Generation Partnership Project 2 (3GPP2), IEEE 802.11 WiFi,Bluetooth, etc. UE1 may communicate with its serving access point (e.g.,AP1 102) through a forward link 112 and a reverse link 114. UE1 may alsoreceive signals from other access points (e.g., AP2 104 and/or AP3 106).It should be noted that although only a few UEs and APs, and only one LSare illustrated in FIG. 1, any number of each of these devices may bepresent in the system 100.

Location server 110 may store signal strength information, timinginformation and/or other signal related information corresponding todifferent APs (e.g., Wi-Fi heat maps) on a grid of points. Theinformation stored by LS 110 may be calculated by LS 110 (or by someother entity and then provided to LS 110) based on known characteristicsof APs (e.g., AP locations, transmission power, antenna characteristics,radio technology) and information about the coverage area of APs (e.g.,local terrain, building floor plans, building materials). Theinformation stored in LS 110 may also or alternatively be compiled fromsignal measurements of APs made by mobile devices (and/or by other APs)specifically assigned to measure signal characteristics of APs and tosend the measurements to a server (e.g., location server 110) viacrowdsourcing as a background task. The information stored in LS 110 maycorrespond to calculated and/or measured signal characteristics for eachAP (e.g., mean RSSI, mean RTT) at each of a number of grid pointsdistributed over the coverage are of the AP. For example, the gridpoints may correspond to a rectangular array oriented in a certaindirection and containing rows and columns of grid points in which thedistance between adjacent grid points along each row or column may befixed and small (e.g., one meter). LS 110 may provide some or all of thestored information to the UEs (e.g., UE1, UE2 and UE3) and/or to otherdevices.

In order to precisely identify a set of grid points, first, a boundingbox may be considered that covers a region of interest. Multiple gridpoints may be defined within the bounding box. Typically, the gridpoints are uniformly distributed within the region of interest. As anexample, the grid points may reside at the corners of, or at the centersof, square-shaped cells. In general, the cells may have any other shape,such as a square, rectangle, hexagon, circle, ellipse, etc. withoutdeparting from teachings of the present disclosure.

Signals corresponding to an access point may be measured or computed(e.g., based on a local building layout and known RF propagation laws)for each of the grid points to generate a heat map. The heat map may bestored in a location server or any other devices in a wirelesscommunication system. The heat maps may then be provided (e.g., bylocation server 110) to one or more mobile devices (e.g., UE1, UE2 andUE3) in the vicinity of the access point. As an example, the heat mapsmay be provided to a mobile device by a location server using the SUPLlocation solution defined by the Open Mobile Alliance (OMA). The heatmaps may also be provided using the Long Term Evolution (LTE)Positioning Protocol (LPP) Extensions protocol defined by OMA which isknown as LPPe. In addition, a mobile device (e.g., UE1, UE2 or UE3) mayrequest a heat map from a location server (e.g., location server 110)using SUPL or LPPe and may provide its capabilities to the locationserver to support receipt of a heat map using SUPL or LPPe.

As an example, a Wi-Fi heat map may be generated for an access point.Considering that the Wi-Fi signal may have a range of close to 100meters, if grid points are located at 1 meter apart, 40,000 grid pointsmay be considered for each AP, as described in an earlier example. Evenif a signal characteristic (e.g., mean RSSI or mean RTT) correspondingto each grid point takes only one octet, the amount of information thatneeds to be stored/communicated with each mobile device per signalcharacteristic and per AP may be equal to 40,000 octets. In addition,the mobile device may receive information corresponding to multiple APsin its vicinity and for several signal characteristics, which can easilyamount to megabytes of information.

Other information that be stored in location server 110 for each AP mayinclude a location area comprising a coverage area of the AP (e.g.,expressed in geographic form and/or in civic form), the type of thelocation area (e.g., whether indoors, outdoors or partly indoors andpartly outdoors) and characteristics of the AP such as manufacturer andmodel. This additional information may be provided by LS 110 to one ormore mobile devices (e.g., UE1, UE2 and UE3). The additional informationmay be provided in a compact form to reduce signaling, processing anddata storage in LS 110 and/or in each recipient mobile device, asdescribed further down herein. The additional information may beconfigured in LS 110 by an operator (e.g., based on known data for thedeployed APs such as AP1, AP2 and AP3). Alternatively or in addition,the additional information may be provided to LS 110 or to a serverwhich can transfer the information to LS 110 by the APs (e.g., AP1, AP2and AP3) and/or by mobile devices (e.g., UE1, UE2 and UE3) usingcrowdsourcing.

FIG. 2 illustrates an example reference frame 200 that can be defined toprovide a local coordinate system and enable heat maps for some indoor(or outdoor) area 202 such a building, shopping mall, sports arena, andthe like. The reference frame 200 may be used to define a set of gridpoints that may serve as the basis for determining heat maps for one ormore access points. In FIG. 2, the location and orientation of thereference frame may be specified relative to a fixed point 204 whoselocation may be specified using absolute geographic coordinates (e.g.,latitude, longitude and altitude) or by civic means (e.g., using apostal address and/or building designation such as “Main front entranceto shopping mall XYZ in city ABC” where XYZ and ABC are publicly knownnames). An origin 206 for the reference frame 200 may then be defined byrelative displacements in directions North (or South), East (or West)and up (or down) from the fixed point 204. The reference frame may havehorizontal and perpendicular X and Y coordinate axes, designated X_(RF)and Y_(RF), respectively, in FIG. 2, through the origin 206. Orientationof the reference frame is defined by a clockwise orientation angle φbetween the direction of true North and the Y axis Y_(RF). In oneembodiment, a range of zero to 89 degrees may be used for cp. In anotherembodiment, the range of φ may be zero to 359 degrees.

The reference frame 200 in FIG. 2 may be used to define a horizontal andrectangular bounding box 208 containing grid points associated with anRF heat map for an AP. The sides of the bounding box 208 may be parallelto the X_(RF) and Y_(RF) axes of the reference frame 200. In FIG. 2,W_(BB) represents the width of the bounding box 208 (parallel to theX_(RF) axis) and L_(BB) represents the length of the bounding box 208(parallel to the Y_(RF) axis). Within the reference frame 200, ahorizontal rectangular grid of points (described later in associationwith FIG. 3) may be defined where rows of grid points are parallel tothe X_(RF) axis and columns of grid points are parallel to the Y_(RF)axis. The distance between adjacent grid points along each row and alongeach column may the same and fixed and may be used as the unit of lengthfor other distances associated with the reference frame 200 such as thelength L_(BB) and the width W_(BB) of the bounding box 208. One of thegrid points may coincide with the origin 206 for the reference frame200.

The position of the bounding box 208 may be defined relative to thereference grid 200 to include all or part of the coverage area of aparticular AP and/or all or part of an area of interest such as indoorarea 202. The bounding box 208 may have a local origin 210 which may bea corner of the bounding box with minimum X and Y coordinates (alsoreferred to as offsets), shown as X_(min) and Y_(min) in FIG. 2. Thevalues of X_(min) and Y_(min) in units of the fixed inter grid pointspacing may each be exact integers, meaning that there may be one gridpoint exactly at the local origin 210. Local X and Y coordinate axes,X_(BB) and Y_(BB), through the local origin 210 may then be defined thatare parallel to the coordinate axes, X_(RF) and Y_(RF), respectively,for the reference frame 200.

FIG. 3 illustrates more details for the bounding box 208 in FIG. 2 andillustrates a set of grid points 212 that are within, or along theperimeters of the bounding box 208, in accordance with certainembodiments of the present disclosure. The set of grid points 212 may bedefined relative to the reference frame 200 as described previously inassociation with FIG. 2. Thus, the grid points 212 may include one gridpoint at the local origin 210 of the bounding box 208 and additionalgrid points along rows and columns parallel to the local X_(BB) andY_(BB) axes. The grid points 212 are separated by a fixed inter-gridpoint distance (or spacing) D. Since the length L_(BB) and the widthW_(BB) of the bounding box 208 are each an integer multiple of theinter-grid point distance D, as described earlier for FIG. 2, the set ofgrid points 212 may include other grid points aligned with the othercorners of the bounding box 208, as shown in FIG. 3, and grid pointsalong and aligned with each of the four sides of bounding box 208, asfurther illustrated in FIG. 3. Grid points may each be assigned localcoordinates [x,y] where x specifies the local X coordinate of the gridpoint along the local X_(BB) axis in units of the distance D, and yspecifies the local Y coordinate of the grid point along the localY_(BB) axis in units of the distance D. For example, the coordinates ofthe grid point at the local origin 210 will be [0,0] and with thecoordinates of some other grid points nearby to the local origin 210 asalso shown in FIG. 3. The inter-grid point distance D may be defined inunits of decameters, meters, decimeters, or any other units. In certainembodiments, the distance between the grid points in X versus Ydirections may be different, without departing from teachings of thepresent disclosure.

The set of grid points 212 in FIG. 3 may be used to provide signalcharacteristics (e.g., RSSI and/or RTT) for one or more APs (e.g., an APor APs whose coverage area partly or completely overlaps with thebounding box 208). Values for each signal characteristic (e.g., meanRSSI, mean RTT) may be obtained by calculation and/or measurement foreach of the grid points in the set of grid points 212. As describedpreviously, if these values are provided (e.g., to a mobile device)without any compression or special encoding, the amount of data may bevery large. Therefore, the values for each signal characteristic may beencoded and compressed.

One of the parameters associated with such encoding and compression maybe the order in which signal values are compressed and encoded asdefined by the order in which their associated grid points in the set ofgrid points 212 are scanned. FIGS. 4 and 5 illustrate two examplescanning orders that may be used to scan the set of grid points 212. Thescanned information may then be encoded and stored in a device and/orcommunicated with other devices.

FIG. 4 illustrates an example scanning order 400 for encoding data in aheat map (e.g., to encode mean RSSI and/or RSSI standard deviationvalues) using the set of grid points 212 illustrated in FIG. 3. Asillustrated, scanning may start from the local origin 210 of thebounding box 208 which has local X and Y coordinates [0,0] and maycontinue along the local X_(BB) axis and thus along the first and bottomrow from left to right in this illustration. In this example,information may be obtained and encoded for the sequence of grid pointswith local coordinates [0,0], [1,0], [2,0], [3,0] and so on until theend of the row with coordinates [9,0] in this example is reached. Whenall the points on the first row of the grid are scanned, the grid pointsin the second row which have a local Y coordinate of 1 may be scannedstarting from the leftmost grid point (on the local Y_(BB) axis). Whenthe end of this row is reached, grid points along the next row with alocal Y coordinate of 2 may be scanned starting with the grid point atthe left on the local Y_(BB) axis. In the example shown in FIG. 4, thegrid points may thus be scanned with the following order: [0,0], [1,0],[2,0], [3,0], . . . , [9,0], [0,1], [1,1], [2,1], . . . , [9,1], [0,2],[1,2], [2,2], [3,2] . . . . The last row to be scanned in this examplewould be the top row with a local Y coordinate of 6.

In one embodiment, RSSI values may be determined (e.g., by a locationserver such as location server 110) for each grid point in a set of gridpoints 212 within or along the perimeter of a bounding box 208 by eithercalculation and/or measurement. As an example, the RSSI values may becalculated based on a plurality of predetermined parameters, such as APtransmission power and antenna gain, AP location, building or otherindoor structural layout, RF propagation physical laws, and the like. Inanother example, RSSI values may be measured by one or more mobiledevices at different locations. The mobile devices may send the measuredvalues to the location server for storage and/or further analysis. As anexample, the location server may generate heat map informationcorresponding to a set of grid points 212 based on the measurements.

In one embodiment, the RSSI values may be encoded without compressionfor each grid point—e.g., using a single octet for each value expressinga value between 0 and 255, where the RSSI value V1 in units of decibelmilliwatts (dBm) may be given by the encoded value V2 by some knownrelationship such as:V1=(127−V2)dBm  Eqn (1)

Next, the uncompressed values (e.g., the encoded values V2 for equation(1) may be scanned by scanning the associated grid points using adefined scanning order (e.g., as illustrated in FIG. 4). As each gridpoint is scanned, the uncompressed RSSI value (e.g., in the range 0 to255 and encoded using 8 bits) corresponding to the grid point currentlybeing scanned may be compressed to be stored in a smaller number ofbits. The compressed bits may be added to one or more strings of bitsrepresenting the entire compressed heat map associated with the set ofgrid points 212 for the bounding box 208 and the particular AP.

Compression of RSSI values may be based on (i) obtaining a delta valuefor each grid point based on the difference between the RSSI value forthe grid point and the RSSI value for the previous grid point in thescanning order; (ii) obtaining double delta values based on thedifferences between delta values for adjacent grid points; or (iii) useof JPEG compression. Details of delta and double delta compressiontechniques are disclosed in a co-pending patent application entitled“Techniques For Compressing RF Heat Maps For Access Points.”

Aligning Heat Maps Corresponding to Different APs

Typically, each AP may have one or more unique heat maps providingexpected (e.g., calculated or measured) RSSI or RTT values for a set ofgrid points corresponding to a bounding box. If a mobile device receivesone or more heat maps for each of a plurality of APs (e.g., each heatmap being defined with a bounding box and set of grid points that areunique for each AP), the mobile device may have to perform extraprocessing to align all the received information corresponding todifferent grid points.

FIG. 5 illustrates two example APs with their corresponding heat maps,and a mobile device in their vicinity. As illustrated, heat map 506corresponds to AP1 502, and heat map 508 corresponds to AP2 504. Amobile device 510 (e.g., which may correspond to UE1 108 in FIG. 1) mayreceive heat map information for both AP1 and AP2—e.g., from a locationserver such as LS 110 in FIG. 1 (not shown in FIG. 5). The heat map 506corresponding to AP1 overlaps with a portion of the heat map 508corresponding to AP2. In this example, grid points associated with thetwo heat maps do not coincide in the overlapping area. As a result,extra processing may be needed to align heat map informationcorresponding to AP1 and AP2 in the overlapping area. For example, themobile device 510 may wish to determine if it is at or near to the gridpoint 512 for the heat map 506. In order to accomplish this, the mobiledevice 510 may measure an RSSI value for the AP1 502 and compare themeasured RSSI to the RSSI provided by the heat map 506 for the gridpoint 512. If the two RSSI values are the same or nearly the same, thenthe mobile device 510 may assume that it may be at or near to the gridpoint 512. But in order to verify this, the mobile device 510 may alsoneed to measure an RSSI value for the AP2 504 and compare the measuredRSSI to an RSSI provided by the heat map 508 for the location of thegrid point 512. If the measured and provided RSSI values are the same ornearly the same, then the mobile device 510 may assume a higherprobability of being at or near to the grid point 512. However, the heatmap 508 does not contain a grid point corresponding to the grid point512 in the heat map 506. Therefore, the mobile device 510 may have toinfer an RSSI value for heat map 508 corresponding to the grid point 512by interpolating between RSSI values for nearby grid points in the heatmap 508 which may add extra processing and/or introduce errors (e.g., ifinterpolation is performed incorrectly). Therefore, it may be beneficialto align the heat maps for different APs (e.g., AP1 502 and AP2 504 inFIG. 5) by using a common bounding box and/or a common set of gridpoints for two or more APs. The common bounding box and/or common set ofgrid points could be optimized for a specific location. For example, theapproximate location of the mobile device may be considered to be at thecenter of the set of grid points and/or the common bounding box. Inanother example, a common bounding box and a common set of grid pointscould be based on building geometry such as by aligning the X and Y axesfor the common bounding box and grid points with the perpendicular sidesof a rectangular shaped building.

In one embodiment, one or more common parameters may be defined fordifferent sets of grid points corresponding to different APs. Forexample, different sets of grid points may have a common origin, commonorientation, and/or common grid point spacing. In addition, one or moredistinct parameters may be defined for the set of grid pointscorresponding to each AP. For example, a displacement of a local originfrom the common origin in units of grid spacing in the X and Ydirections, and/or a length and a width of a bounding box may be definedseparately and uniquely for each AP. As a result, grid points for allgrids corresponding to different APs may be aligned to a common“reference frame”, also referred to as a common “reference grid”. Thecommon reference grid (or reference frame) may be defined based on thecommon origin, common orientation and common grid spacing parameters.Therefore, a mobile device may receive information (e.g., RSSI values)corresponding to different APs at any point on the reference grid.

FIG. 2 illustrates aspects of heat maps, grid points, bounding boxes andreference frames (or reference grids) that may be either common to a setof APs or distinct for each AP. In FIG. 2, the reference frame 200, alsoreferred to herein as a reference grid, may be common to some or to allAPs. The definition of the reference frame 200 that is common to some orall APs may include the location of the origin 206 relative to the fixedpoint 204, the location of the fixed point 204, the orientation φ of theX_(RF) and Y_(RF) axes and the inter-grid point distance D shown in FIG.3. Conversely, for any AP, a particular bounding box and associated heatmap values (e.g., mean RSSI values or mean RTT values) for each gridpoint may be unique to that AP. For example, the bounding box 208 shownin FIG. 2 including the offsets X_(min) and Y_(min) of the local origin210 relative to the origin 206 and the length L_(BB) and width W_(BB)may be unique to just one AP or to some but not to all of the APs forwhich the reference frame 200 is common. Furthermore, signalcharacteristics (e.g., mean RSSI, mean RTT) that are measured orcalculated for each grid point in the bounding box 208 (e.g., for eachof the set of grid points 212 shown in FIG. 3) may be unique to a singleAP. Consequently, any heat map derived from these signal characteristicsthat may be encoded with or without compression (e.g., compression basedon delta values, double delta values or JPEG) may also be unique to aparticular AP.

FIG. 6 illustrates another example of a common reference frame 610 (alsoreferred to as a common reference grid) that may be used to provide heatmap information corresponding to multiple APs. As illustrated, thereference frame 610 may have an origin 620 (e.g., whose location isdefined relative to some fixed point not shown in FIG. 6), anorientation of θ relative to North and an inter-grid point spacing of G.The reference frame 610 may be used to define a bounding box andassociated heat map information for AP1 602 and AP2 604. In the case ofAP 602, the bounding box is 606 and in the case of AP 604, the boundingbox is 608. The bounding boxes 606 and 608 are different but make use ofthe same set of grid points due to sharing the common reference frame610. Therefore, the grid points in the bounding boxes 606 and 608 arealigned in the area where the bounding boxes overlap, thereby avoidingthe problems of non-aligned grid points exemplified in FIG. 5 when heatmaps associated with the bounding boxes are provided for each of the APsto some mobile device.

As discussed previously, there may be common information for two or moreAPs, such as a common reference frame (or common reference grid) and itsvarious parameters and unique information for each AP such as a uniquebounding box (and its various parameters) and a unique heat map (e.g.,encoding mean RSSI or mean RTT associated with grid points within thebounding box). Both the common information and the unique informationmay be stored and maintained within a server, such as the locationserver 110 of FIG. 1. This information may be transferred to one or moremobile devices, such as UE1 108 in FIG. 1, when requested by a mobiledevice or when the server detects that a mobile device may be at alocation where the information may be useful. A mobile device may usethe information, after it has been transferred, to determine or helpdetermine its location. For example, UE1 108 in FIG. 1 may receive fromLS 110 a heat map encoding mean RSSI values for AP1 102, another heatmap encoding mean RTT values for AP1 102 and similar pairs of heat mapsfor mean RSSI values and mean RTT values for AP2 104 and AP3 106. TheUE1 108 may make measurements of the RSSI and/or RTT for each of the APs102, 104 and 106 at some location and may compare the measured RSSIand/or measured RTT values to the expected RSSI values and/or expectedRTT values for each of the APs 102, 104 and 106 as obtained from theheat maps received from LS 110. The UE1 108 may use the comparison todetermine a probable location for UE1 108 where the measured andexpected RSSI and RTT values most closely match one another.

In order to reduce storage, signaling and processing in LS 110 and UE1108 and in order to reduce management of the data in LS 110 (e.g., by aprogram or human operator), the common information for APs 102, 104 and106 (e.g., a common reference grid) may be stored and sent once only forall three APs. Conversely, the unique information for each of the APs102, 104 and 106 (e.g., a definition of a bounding box for each AP andone or more heat maps defined relative to this bounding box) may bestored and sent individually for each AP. Similar treatment of commonversus unique information may be applied to other types of informationfor the APs 102, 104 and 106 that may be sent to UE 108 to assist UE 108in determining its location in order to reduce storage, signaling andprocessing and in order to make management of common information moreefficient in LS 110.

In one embodiment, in order to achieve more efficient support for commoninformation related to APs in a standard generic manner and avoiddifferent conventions for defining and transferring common information,the use of group data may be employed. Group data may refer to datarelated to a group of two or more APs that is common to the APs in thegroup, but not necessarily common to APs that are not in the group. Forany set of APs (e.g., all APs in a particular building), differentgroups of APs may be defined that have certain information in common. Asan example, a group of APs could include all APs for which a commonreference grid is used to define bounding boxes and heat maps asdescribed earlier. A group of APs could also or instead include all APson the same floor of a building (and thus all APs whose floor level inthe building is the same), or all APs in the same portion of a building(e.g., all APs in the same terminal at an airport or all APs in the samewing of a hospital). A group of APs could also include all APs thatshare the same manufacturer and have the same model type. Informationfor a set of APs may then be structured into one or more sets of groupdata where each set of group data applies to a group of two or more APs.In addition to the group data, individual data may be defined thatapplies only to individual APs. The use of group data may significantlyreduce the amount of data that needs to be uniquely stored and providedfor each AP, thereby reducing data storage, signaling and processing andmay also reduce management and configuration of data in a server.

The use of group data is exemplified in FIG. 7 for the three APs 102,104 and 106 in FIG. 1. FIG. 7 shows sets of data that may be defined,stored (e.g., in LS 110 or UE1 108) and transferred (e.g., from LS 110to UE1 108). Each set of data is represented in FIG. 7 by a rectangularbox and contains items that are summarized within each box. Some of thesets of data in FIG. 7 are unique to each AP and include data 720 forAP1 102, data 740 for AP2 104 and data 760 for AP3 106. Other sets ofdata in FIG. 7 apply to groups of two or more APs and include data 780for a Group 1 of APs, data 784 for a Group 2 of APs and data 788 for aGroup 3 of APs.

Group 1 includes all three APs 102, 104 and 106; Group 2 includes AP1102 and AP2 104 but not AP3 106; and Group 3 includes AP1 102 and AP3106 but not AP2 104. Group 1 data 780 includes data related to a commonreference grid (or reference frame) and may include an identity forGroup 1 (e.g., some number or name assigned to indicate Group 1), aversion (e.g., a version number) that may be changed (e.g., incrementedby one) whenever any data in the Group 1 data 780 changes, a validityperiod which may indicate a period of time over which the Group 1 data780 may be considered valid by a recipient mobile device (e.g., UE1 108)and/or information for a reference grid.

The information for the reference grid may be included within Group 1data 780 or may be separate but linked (as shown by the data 782 in FIG.7) and may include the location of an origin, an orientation and aninter-grid point spacing. Group 2 data 784 includes data related to acommon location area for a set of APs (e.g., APs 102 and 104 in theexample of FIG. 7) and may identify a common coverage area for the APsor a common area containing part or all of the coverage area of each AP(e.g., one floor of a building or part of one floor of a building).Similar to Group 1 data 780, Group 2 data 784 may include an identityfor Group 2 (e.g., a number or name that is different from the number orname used for the identity of Group 1), a version and/or a validityperiod. Unlike Group 1 data 780, Group 2 data 784 may include datarelated to a common location area which may be part of Group 2 data 784or, as shown in FIG. 7, may be separate but linked to Group 2 data 784in location area data 786.

Location area data 786 may include a description of a common coveragearea for APs 102 and 104 or an area partly or completely containing thecoverage areas for APs 102 and 104 that may include a geographic areadescription (e.g., for a circle, ellipse or polygon), a civic areadescription (e.g., the address and/or name of a building and a floorlevel and/or set of room or suite designations) and/or an indication ofwhether a mobile device is able to change its altitude (e.g., move up ordown by one or more floors via stairs, an escalator or an elevator) fromwithin the location area. An indication of whether or not an altitudechange is possible from within the location area may assist a mobiledevice (e.g., UE1 108) that has the location area data to determinewhether its altitude may have changed subsequent to entering thelocation area.

The location area data 784 or associated data 786 may also include otherdata such as: (i) a description of the type of location area (e.g.,whether indoors, outdoors, or partly indoors and partly outdoors); (ii)a description of a particular type of indoor or outdoor area (e.g.,walled office area, cubicle offices, high ceiling, large open space,parking garage, outdoor urban, outdoor suburban); (iii) a description ofthe horizontal coverage of the location area (e.g., the size of thelocation area as a percentage of the total contiguous horizontal area,such as a floor in a building, of which this location area is a part);(iv) a description of the vertical coverage of the location area (e.g.,the percentage of the total number of floors or levels in a building orstructure, including sub-levels, of which this location area is a part)and/or whether the location area has exterior access (e.g., such asexterior access from a location area within one building to anotherbuilding via a doorway, opening or bridge).

Group 3 data 788 may include data similar to Group 1 data 780 and Group2 data 784 including an identity for Group 3 (e.g., a number or namethat is different from the numbers or names used for the identities ofGroup 1 and Group 3), a version and/or a validity period. Unlike Group 1data 780 and Group 2 data 784, Group 3 data 788 may include commonproperties for the APs that are members of Group 3 which, in thisexample, include AP 102 and AP 106. The AP properties may be part ofGroup 3 data 788 or, as shown in FIG. 7 may be separate from but linkedto Group 3 data 788 via the data 790. Data 790 may include theidentification of a common manufacturer for APs 102 and 106, theidentification of a common model of AP, the identification of a commonchip manufacturer and/or chip model, and/or the identification of acommon type of AP (e.g., an AP that supports IEEE 802.11a, 802.11g,802.11n or a particular version of Bluetooth). The AP properties 790 maybe useful to UE1 108 to help UE1 108 determine its location since thedata may assist UE1 108 to predict the RSSI or RTT values for each AP inGroup 3 (i.e., AP 102 and AP 106) at any particular distance from the APand/or may assist UE1 108 to adjust or calibrate RSSI or RTT valuesreceived for AP 102 or AP 106 in a heat map (e.g., from LS 110).

As mentioned above, data provided to UE1 108 for APs 102, 104 and 106may also include unique data for each AP as shown by data 720 for AP102, data 740 for AP 104 and data 760 for AP 106. For each AP, theunique data may include the identity of the AP (e.g., a Media AccessControl (MAC) address for the AP), the location of the AP (e.g., alatitude, longitude and altitude or a location expressed using X and Ycoordinates using the common reference grid for the APs defined inreference grid data 782) and/or one or more heat maps for the AP (e.g.,a heat map containing encoded values for mean RSSI or mean RTT) for gridpoints in a bounding box defined as part of the unique data for each APor defined as part of the heat map. In addition, the unique data foreach AP may identify the groups to which each AP belongs. Thus forexample, the unique data 720 for AP 102 may include identifications forGroups 1, 2 and 3 since AP 102 belongs to each of these groups.Similarly, the unique data 740 for AP 104 may include identificationsfor Groups 1 and 2 but not Group 3, since AP 104 belongs to these twogroups, and the unique data 760 for AP 106 may include identificationsfor Groups 1 and 3 but not Group 2, since AP 106 belongs to each ofthese groups.

By including identifications for each group in both the group data andthe unique data for each AP, it is possible to indicate the groups thateach AP belongs to and to associate the group data for these groups tothe member APs. A mobile device that receives group data for a set ofAPs (e.g., receives Group 1 data 780, Group 2 data 784 and Group 3 data788 as well as associated data 782, 786 and 790 in FIG. 7) from alocation server such as LS 110 and/or from one or more APs (such as AP102, 104 and/or 106 in FIG. 7) may use the data to determine or helpdetermine vicinity related information for the APs. For example in thecase of FIG. 7, a mobile device (e.g., UE1 108) that receives all thedata illustrated and described earlier for FIG. 7 may use the data todetermine RSSI and/or RTT values for each of the APs at different setsof grid points within the coverage area of each AP. The mobile devicemay further use this vicinity related information to determine or helpdetermine its location based on measurements by the mobile device ofRSSI and RTT for the different APs as described earlier.

Although FIG. 7 shows only three APs and data for three groups, themethod may be extended to any number of APs and any number of groups.The groups shown in FIG. 7 define common data for a reference grid orreference frame (in the case of Group 1), common data for a locationarea (Group 2) and common data for AP properties (Group 3). But othertypes of common data may be defined and associated with APs by means ofgroup data. In addition, certain types of group data may be repeated.For example, there may be (i) two or more sets of group data, denotedRG1, RG2, RG3 . . . , each defining a different reference grid; (ii) twoor more sets of group data, denoted LA1, LA2, LA3 . . . , each defininga different location area and/or (iii) two or more sets of group data,denoted P1, P2, P3, . . . , each defining a different set of APproperties.

An AP may belong to one of each of the types of groups and thereby beassociated with the corresponding group data. For example, an AP A1 maybe associated with group data RG1, LA1 and P1, whereas another AP A2 maybe associated with group data RG2, LA2 and P2. In addition, an AP maybelong to more than one group of the same type and thereby be associatedwith more than one set of group data of the same type. Thus, in theprevious example AP A1 may be associated with group data RG1 and groupdata RG2, while AP A2 may be associated with group data LA1 and LA2 andwith group data P1 and P2. Allowing an AP to use more than one type ofgroup data may provide an efficient means of defining additional datafor the AP.

For example, in the case of an AP that is associated with two or morecommon reference grids, several different bounding boxes and associatedheat maps may be defined—for example, a first bounding box andassociated heat map with X and Y axes aligned North-South and East-Westand a second bounding box and associated heat map covering almost thesame area but oriented at say 45 degrees to the first bounding box. Thismay be useful to support heat maps that use the same referencegrid—e.g., in the case of building with different sections where eachbuilding section needs its own reference grid. A mobile device that isin one section of the building can then be provided with heat maps forAPs using the reference grid for the section of the building the mobiledevice is currently located in, thereby ensuring that the heat maps willall be aligned to the same set of grid points. Similarly, an AP may beassociated with group data for two or more location areas, where datafor a first location area may define (for example) a coverage area forthe AP and data for a second location area may define (for example) ageographic area of importance within a building (e.g., a collection ofadjacent gate areas at an airport) within which there is somepossibility that the AP can be received. Further, an AP may beassociated with group data for different sets of AP properties, where afirst set of group data may (for example) provide details about the APmanufacturer while a second set of AP data may (for example) providedetails about the signal types supported by an AP.

Some further examples of using group data are now described. In oneexample, a set of APs in an airport may be distributed over twodifferent terminals (e.g., terminal A and terminal B). One or more heatmaps (e.g., for RSSI or RTT values) may be assembled for each of the APsbased on a reference grid associated with terminal A in the case of APsin terminal A, or based on a reference grid associated with terminal Bin the case of APs in terminal B. The two reference grids may includeone type of group data for the set of APs and other types of group datamay be defined to provide other common data for some or all of the APs,such as common data for a location area and common AP properties.

For example, group data A1 and A2 may be defined for some or all of theAPs that are located in terminal A and group data B1, B2 and B3 may bedefined for some or all of the APs that are located in terminal B of theairport. Group data A1 may define a common reference grid associatedwith terminal A for APs in terminal A and group data A2 may define acommon location area (e.g., the geographic area for terminal A) for APsin terminal A. Similarly, group data B1 may define a common referencegrid associated with terminal B for APs in terminal B, group data B2 maydefine a common location area (e.g., the geographic area for terminal B)for APs in terminal B and group data B3 may define common properties(e.g., manufacturer, model) for APs in terminal B. Another set of groupdata, group data C, may be defined for APs in both terminals A and B ifthere is any data common to all of the terminals—e.g., data related tosupport of a common IEEE 802.11 or Bluetooth signaling standard.

In one embodiment, an AP may belong to multiple groups, each group beingdifferent in terms of one or more characteristics. For example, in abuilding, different location area groups (such as location area Group 2in FIG. 7) may be defined for different floors (first floor group,second floor group, etc.). In one embodiment, a location server ensuresthat all the APs that are identified as being a part of each group sharea common floor level. In one embodiment, information corresponding toeach group includes an indication of whether a change of altitude withinthe shared area is possible.

In one embodiment, an AP may belong to more than one location areagroup—e.g., if location areas partially overlap. In the example of FIG.7, this could mean that AP 102 belongs to both Group 2 containing datafor one location area and another group (not shown in FIG. 7) containingdata for some other location area. A mobile device and a location servermay use location area groups to help determine when assistance data foradditional APs needs to be sent to the mobile device. For example, if amobile device reports visible APs belonging to certain location areagroups, the location server may provide assistance data for these APsand other APs in the same location area group. If a mobile devicedetects APs that do not belong to any known location area groups, themobile device may request assistance data for these APs and may expectto receive data for these APs and possibly for other APs in the samelocation area groups as these APs.

In one embodiment, a mobile device may communicate with an AP andreceive an access point group identifier from the AP. The mobile devicemay obtain a plurality of characteristics corresponding to the AP basedon the received group identifier from a data base (e.g., located at themobile device and/or a location server). In one embodiment, assistancedata may be provided to a mobile device for a group of APs. Assistancedata may be provided in the form of group data that is common to all APsin the group. The group data may be associated with a group ID. As anexample, in the case of UE1 108 and AP 102 in FIG. 1, UE1 108 maycommunicate with AP 102 and receive the identity of the Group 1, theGroup 2 and/or the Group 3 shown in FIG. 7 from AP 102. UE1 108 may thenobtain the Group 1 data 780, the Group 2 Data 784 and/or the Group 3Data 788, as well as the data associated with each group including data782, data 786 and/or data 790 from a server such as LS 110.

In another embodiment, a mobile device such as UE1 108 may requestassistance data from a location server, such as LS 110, by sending amessage to the location server (e.g., a message conforming to the SUPLlocation solution and/or to LPPe, and the like). The message may providegroup IDs and group version numbers that identify the group data thatthe mobile device already has (e.g., by previous transfer from thelocation server). The message may further identify APs (e.g., using aMAC address for each AP) for which the mobile device has alreadyreceived individual unique data from the location server. The messagemay also provide an approximate location for the mobile device and/ormay identify one or more APs (e.g., using their MAC addresses) currentlyor recently visible to the mobile device.

The location server may then send unique AP data to the mobile devicefor one or more APs and/or may send one or more sets of group dataapplicable to these APs and/or to other APs. The unique AP data may befor APs nearby to the approximate location of the mobile device and/orfor APs indicated as being visible or recently visible to the mobiledevice. The group data may be for groups of APs that include APs forwhich unique data is sent to the mobile device and/or that include APsnearby to the approximate location of the mobile device and/or thatinclude APs visible to or recently visible to the mobile device.

In an embodiment, the location server may refrain from sending uniquedata for APs for which the mobile indicated it already has the uniquedata. In a further embodiment, the location server may refrain fromsending group data to the mobile device for groups for which the mobiledevice indicated it already has data. However, if the mobile deviceindicates it has group data associated with a particular group ID andversion, a location server may send new group data if the versionindicated by the mobile device is no longer the most recent version forthis group and if the group data has changed significantly. In someembodiments, a location server may send unique AP data and/or group datato a mobile device (e.g., using SUPL and/or LPPe) without receiving arequest from the mobile device. For example, a location server may sendunique data and/or group data for APs in a certain part of a building toa mobile device when measurements (e.g., AP measurements) or a locationestimate sent by the mobile device to the location server indicate thatthe mobile device is within or nearby to this part of the building(e.g., such as when a user of the mobile device uses an elevator totravel to a new floor in a building and the mobile device has little orno data for APs present on this new floor).

As a particular example of such updating of data for APs and referringto FIGS. 1 and 7, the UE1 108 may have data 720 for AP 102 and Group 1data 780 and linked data 782 but may not have data for APs 104 and 106or Group 2 data 784 or Group 3 data 788. UE1 108 may then send a requestfor more AP data to LS 110 and may indicate that it has data for AP 102and has data for Group 1. UE1 108 may further provide a locationestimate and/or indicate that AP 104 and/or AP 106 are visible. Based onthis request, LS 110 may then send to UE1 108 data 740 for AP 104, data760 for AP 106, Group 2 data 784 (and linked data 786) and Group 3 data788 (and linked data 790). UE1 108 may then use the data to determine orhelp determine its location at the current time and/or at a later time.For example, UE1 108 may use RSSI and/or RTT heat maps received as partof AP 104 data 740 and AP 106 data 760 combined with common referencegrid data from Group 1 data 780 (and linked data 782) to help determineits location from RSSI and/or RTT measurements by UE1 108 of APs 104 and106.

Group data of the type described previously and exemplified in FIG. 7may or may not be hierarchical. For example, four APs denoted A, B, Cand D, may be associated with three different sets of group data G1, G2and G3, where G1 provides group data for all four APs (A, B, C and D),G2 provides group data for APs A and B (but not for APs C and D), and G3provides group data for APs C and D (but not for APs A and B). In thisexample, the data may form a hierarchy starting with group data G1 whichapplies to all APs, then proceeding to group data G2 and G3 which eachprovide data for different non-overlapping sets of APs (A and B in oneset and C and D in the other set) and finally proceeding to any uniquedata for each of the individual APs A, B, C, and D that may not becommon to any of the other APs.

In another example, similar to the previous one, four APs denoted A*,B*, C* and D*, may be associated with three different sets of group dataG1*, G2* and G3*, where G1* provides group data for all four APs (A*,B*, C* and D*), G2* provides group data for APs A*, B* and C* (but notfor AP D*), and G3* provides group data for APs B*, C* and D* (but notfor AP A*). In this example, the data may not form a hierarchy startingwith group data G1* which applies to all APs (A*, B*, C* and D*),because group data G2* and group data G3* provide data for two sets ofAPs (A*, B* and C* in one set and B*, C* and D* in the other set) thatare different sets but also overlapping sets (due to inclusion of APs B*and C* in both sets). Support of different but overlapping sets is not anormal feature of a hierarchy. By allowing both hierarchical andnon-hierarchical data association, the group data method may provideextra flexibility in providing assistance data for APs to a mobiledevice.

FIG. 8 illustrates example operations 800 that may be performed by adevice to provide assistance data corresponding to a plurality of APs(e.g., APs 102, 104 and 106). For example, the device may be a locationserver such as LS 110. At 802, the device provides first assistance datato a mobile device such as UE1 108. The first assistance data mayinclude first group data that is common among the plurality of APs.Moreover, the first group data is associated with a first group ID.

The device may determine the first group data by analyzing one or morecharacteristics of the first plurality of APs. In one example, the firstgroup data includes information corresponding to a common location areafor the plurality of APs. In another example, the first group dataincludes an indication of whether an altitude change is allowed withinthe common location area. In yet another example, the first group dataincludes information corresponding to a reference grid that may be usedin determining the set of AP-specific information. In addition, thefirst group data may include a version and a period during which thedata is valid. The first group data may also include some of the commonproperties of APs, such as an identification of the AP manufacturer, APmodel, a chip manufacturer, a chip model, a signaling type and any otherproperties.

Referring back to FIG. 8, at 804, the device provides the first group IDand a set of AP-specific information for at least one of the pluralityof APs. The plurality APs may comprise WiFi APs, Bluetooth APs, smallcells, Femto cells and/or other types of APs and the assistance data maybe provided at 802 and 804 using SUPL, LPPe and/or any other signalingprotocol.

The device may also provide a second set of assistance data to themobile device corresponding to a second plurality of APs. The secondassistance data may be different from the first assistance data. Thesecond assistance data may include a second group data that is commonamong the second plurality of APs. The second group data may beassociated with a second group ID. In one example, the second pluralityof APs may include at least one of the APs in the first plurality ofAPs. In addition, the device may provide the second group ID to themobile device. In one embodiment, at least one of the APs in the firstplurality of APs or in the second plurality of APs is not in both thefirst and the second plurality of APs.

FIG. 9 illustrates example operations 900 that may be performed by amobile device (e.g., UE1 108) to obtain assistance data corresponding toa plurality of APs (e.g., APs 102, 104 and 106). At 902, the mobiledevice receives first assistance data from a device (e.g., a locationserver such as LS 110). The first assistance data may include firstgroup data that is common among the plurality of APs. The first groupdata may be associated with a first group ID. At 904, the mobile devicereceives the first group ID and a set of AP-specific information for atleast one AP among the plurality of APs. At 906, the mobile devicedetermines AP vicinity information corresponding to the at least one APbased on the first group ID and the set of AP-specific information. Theplurality APs may comprise WiFi APs, Bluetooth APs, small cells, Femtocells and/or other types of APs and the assistance data may be receivedat 902 and 904 using SUPL, LPPe and/or some other signaling protocol.

The mobile device may also receive second assistance data correspondingto a second plurality of APs. The second assistance data may bedifferent from the first assistance data. The second assistance data mayinclude a second group data that is common among the second plurality ofAPs. The second group data may be associated with a second group ID. Inone example, the second plurality of APs may include at least one of theAPs in the first plurality of APs. In one embodiment, at least one ofthe APs in the first plurality of APs or in the second plurality of APsis not in both the first and the second plurality of APs.

FIG. 10 describes one potential implementation of a device 1000 whichmay be used to provide or receive AP vicinity information, according tocertain embodiments. The device 1000 may be a mobile device such as UE1108 in FIG. 1 or a location server such as location sever 110 in FIG. 1.In the embodiment of device 1000 shown in FIG. 10, specialized modulessuch as encoder 1020 may perform any type of encoding of heat maps basedon delta encoding, double delta encoding, JPEG or the like. Device 1000may also or instead perform decoding of AP vicinity information using adecoder 1030—e.g., if device 1000 is a mobile device. These modules maybe implemented to interact with various other modules of device 1000.Memory 1018 may be configured to store data regarding heat maps, and mayalso store settings and instructions regarding grid orientation,spacing, etc. Memory 1018 may also store data unique to one or more APs(such as unique AP data 720, 740 and 780 illustrated in FIG. 7) and/orgroup data such as Group 1 data 780, Group 2 data 784 and Group 3 data788 shown in FIG. 7 (as well as linked data 782, 786 and 790).

In the embodiment shown at FIG. 10, the device 1000 may be a mobiledevice or a location server and include processor 1004 configured toexecute instructions for performing operations at a number of componentsand can be, for example, a general-purpose processor or microprocessorsuitable for implementation within a portable electronic device.Processor 1004 is communicatively coupled with a plurality of componentswithin device 1000. To realize this communicative coupling, processor1004 may communicate with the other illustrated components across a bus1002. Bus 1002 can be any subsystem adapted to transfer data withindevice 1000. Bus 1002 can be a plurality of computer buses and includeadditional circuitry to transfer data.

Memory 1018 may be coupled to processor 1004. In some embodiments,memory 1018 offers both short-term and long-term storage and may in factbe divided into several units. Short term memory may store data whichmay be discarded after an analysis, or all data may be stored in longterm storage depending on user selections. Memory 1018 may be volatile,such as static random access memory (SRAM) and/or dynamic random accessmemory (DRAM) and/or non-volatile, such as read-only memory (ROM), flashmemory, and the like. Furthermore, memory 1018 can include removablestorage devices, such as secure digital (SD) cards. Thus, memory 1018provides storage of computer readable instructions, data structures,program modules, and other data for mobile device 1000. In someembodiments, memory 1018 may be distributed into different hardwaremodules.

In some embodiments, memory 1018 stores software code for a plurality ofapplications 1016. Applications 1016 contain particular instructions tobe executed by processor 1004. In alternative embodiments, otherhardware modules may additionally execute certain applications or partsof applications. Memory 1018 may be used to store computer readableinstructions for modules that implement scanning according to certainembodiments, and may also store compact object representations as partof a database.

In some embodiments, memory 1018 includes an operating system 1014.Operating system 1014 may be operable to initiate the execution of theinstructions provided by application modules and/or manage otherhardware modules as well as interfaces with communication modules whichmay use communications subsystem 1012 which may support wirelesscommunication (e.g., in the case device 1000 is a mobile device) and/orcommunication via wireline links and intermediate networks (e.g., in thecase device 1000 is a location server). Operating system 1014 may beadapted to perform other operations across the components of mobiledevice 1000, including threading, resource management, data storagecontrol and other similar functionality.

In some embodiments, device 1000 includes a plurality of other hardwaremodules (e.g., encoder 1020, decoder 1030). Each of the other hardwaremodules is a physical module within device 1000. However, while each ofthe hardware modules is permanently configured as a structure, arespective one of hardware modules may be temporarily configured toperform specific functions or temporarily activated.

Other embodiments may include sensors integrated into device 1000. Anexample of a sensor can be, for example, an accelerometer, a wi-fitransceiver, a satellite navigation system receiver (e.g., a GPSmodule), a pressure module, a temperature module, an audio output and/orinput module (e.g., a microphone), a camera module, a proximity sensor,an alternate line service (ALS) module, a capacitive touch sensor, anear field communication (NFC) module, a Bluetooth transceiver, acellular transceiver, a magnetometer, a gyroscope, an inertial sensor(e.g., a module the combines an accelerometer and a gyroscope), anambient light sensor, a relative humidity sensor, or any other similarmodule operable to provide sensory output and/or receive sensory input.In some embodiments, one or more functions of the sensors may beimplemented as hardware, software, or firmware. Further, as describedherein, certain hardware modules such as the accelerometer, the GPSmodule, the gyroscope, the inertial sensor, or other such modules may beused in conjunction with the camera and image processing module toprovide additional information. In certain embodiments, a user may use auser input module 1008 to select how to analyze the heat maps.

Device 1000 may include a component such as a communication module 1012,as mentioned above, which may enable device 1000 to communicate withother entities (e.g., APs such as APs 102, 104 and 106 in FIG. 1, otherentities in a network such as entities in wireless network 120 in FIG.1, LS 110 in the case that device 1000 is a mobile device and/or UE1 108in the case that device 1000 is a location server such as LS 110) viawireless or wireline means. Communications module 1012 may supportwireless communication (e.g., if device 1000 is a mobile device) and maythen integrate an antenna and wireless transceiver with any otherhardware, firmware, or software necessary for wireless communications.Such a wireless communication module may be configured to receivesignals from various devices such as data sources via networks andaccess points such as a network access point.

In addition to other hardware modules and applications in memory 1018,device 1000 may have a display output 1010 and a user input module 1008.Display output 1010 graphically presents information from device1000—e.g., to the user in the case that device 1000 is a mobile device.This information may be derived from one or more application modules,one or more hardware modules, a combination thereof, or any othersuitable means for resolving graphical content for the user (e.g., byoperating system 1014). Display output 1010 can be liquid crystaldisplay (LCD) technology, light emitting polymer display (LPD)technology, or some other display technology. In some embodiments,display module 1010 is a capacitive or resistive touch screen and may besensitive to haptic and/or tactile contact with a user. In suchembodiments, the display output 1010 can comprise amulti-touch-sensitive display. Display output 1010 may then be used todisplay any number of outputs associated with a camera or imageprocessing module such as alerts, settings, thresholds, user interfaces,or other such controls.

In the case that device 1000 is a location server (e.g., LS 110 in FIG.1), software or firmware instructions in memory 1018 may be executed onprocessor 1004 to enable device 1000 to perform the example operations800 of FIG. 8 and to transfer unique AP data and group data for APs to amobile device (e.g., to UE1 108 in FIG. 1) using SUPL, LPPe or someother signaling protocol. In the case that device 1000 is a mobiledevice (e.g., UE1 108 in FIG. 1), software or firmware instructions inmemory 1018 may be executed on processor 1004 to enable device 1000 toperform the example operations 900 of FIG. 9 and to receive unique APdata and group data for APs from a location server (e.g., LS 110 inFIG. 1) using SUPL, LPPe or some other signaling protocol.

The methods, systems, and devices discussed above are examples. Variousembodiments may omit, substitute, or add various procedures orcomponents as appropriate. For instance, in alternative configurations,the methods described may be performed in an order different from thatdescribed, and/or various stages may be added, omitted, and/or combined.Also, features described with respect to certain embodiments may becombined in various other embodiments. Different aspects and elements ofthe embodiments may be combined in a similar manner.

Specific details are given in the description to provide a thoroughunderstanding of the embodiments. However, embodiments may be practicedwithout certain specific details. For example, well-known circuits,processes, algorithms, structures, and techniques have been mentionedwithout unnecessary detail in order to avoid obscuring the embodiments.This description provides example embodiments only, and is not intendedto limit the scope, applicability, or configuration of variousembodiments. Rather, the preceding description of the embodiments willprovide those skilled in the art with an enabling description forimplementing embodiments. Various changes may be made in the functionand arrangement of elements without departing from the spirit and scopeof various embodiments.

Also, some embodiments were described as processes which may be depictedin a flow with process arrows. Although each may describe the operationsas a sequential process, many of the operations can be performed inparallel or concurrently. In addition, the order of the operations maybe rearranged. A process may have additional steps not included in thefigure. Furthermore, embodiments of the methods may be implemented byhardware, software, firmware, middleware, microcode, hardwaredescription languages, or any combination thereof. When implemented insoftware, firmware, middleware, or microcode, the program code or codesegments to perform the associated tasks may be stored in acomputer-readable medium such as a storage medium. Processors mayperform the associated tasks. Additionally, the above elements maymerely be a component of a larger system, wherein other rules may takeprecedence over or otherwise modify the application of variousembodiments, and any number of steps may be undertaken before, during,or after the elements of any embodiment are implemented.

Having described several embodiments, it will therefore be clear to aperson of ordinary skill that various modifications, alternativeconstructions, and equivalents may be used without departing from thespirit of the disclosure.

What is claimed is:
 1. A method for obtaining assistance data corresponding to a plurality of access points (APs) at a mobile device, comprising: receiving, at the mobile device, first assistance data from a location server, wherein the first assistance data comprises a first group data that is common among the plurality of APs, wherein the first group data is associated with a first group identifier (ID), the group ID, assigned to each AP of the plurality of APs, and wherein the first group data comprises information corresponding to a reference grid that is used in determining AP-specific information corresponding to each of the plurality of APs; receiving, at the mobile device, the first group ID and a set of AP-specific information for at least one AP among the plurality of APs; and determining, by the mobile device, AP vicinity information corresponding to the at least one AP based on the first group ID and the set of AP-specific information, the AP vicinity information indicating a plurality of locations relative to the at least one AP; and receiving, at the mobile device, second assistance data corresponding to a second plurality of APs, wherein the second assistance data comprises a second group data that is common among the second plurality of APs, the second group data being associated with a second group ID, and the second plurality of APs comprising at least one of the APs in the plurality of APs, wherein the second group data comprises information corresponding to a second reference grid, wherein the second reference grid is used in determining the set of AP-specific information.
 2. The method of claim 1, wherein the reference grid comprises at least one of a common grid point spacing, common grid origin, and a common grid orientation.
 3. The method of claim 1, wherein the first group data further comprises at least one of a version and a validity period.
 4. A mobile device for obtaining assistance data corresponding to a plurality of access points (APs), comprising: a communication system; and memory, communicatively coupled to one or more processors, the one or more processors configured to: receive, via the communication system, first assistance data from a location server, wherein the first assistance data comprises a first group data that is common among the plurality of APs, wherein the first group data is associated with a first group identifier (ID), the group ID, assigned to each AP of the plurality of APs, and wherein the first group data comprises information corresponding to a reference grid that is used in determining AP-specific information corresponding to each of the plurality of APs; receive, via the communication system, the first group ID and a set of AP-specific information for at least one AP among the plurality of APs; determine AP vicinity information corresponding to the at least one AP based on the first group ID and the set of AP-specific information, the AP vicinity information indicating a plurality of locations relative to the at least one AP; and receive, via the communication system, second assistance data corresponding to a second plurality of APs, wherein the second assistance data comprises a second group data that is common among the second plurality of APs, the second group data being associated with a second group ID, and the second plurality of APs comprising at least one of the APs in the plurality of APs, wherein the second group data comprises information corresponding to a second reference grid, wherein the second reference grid is used in determining the set of AP-specific information.
 5. The device of claim 4, wherein the reference grid comprises at least one of a common grid point spacing, common grid origin, and a common grid orientation.
 6. The device of claim 4, wherein the first group data further comprises at least one of a version and a validity period.
 7. A non-transitory computer-readable medium comprising processor-executable instructions, the processor-executable instructions, when executed by the one or more processors, cause the one or more processors to: receive, at a mobile device, first assistance data from a location server, wherein the first assistance data comprises a first group data that is common among a plurality of APs, wherein the first group data is associated with a first group identifier (ID), the group ID, assigned to each AP of the plurality of APs, and wherein the first group data comprises information corresponding to a reference grid that is used in determining AP-specific information corresponding to each of the plurality of APs; receive, at the mobile device, the first group ID and a set of AP-specific information for at least one AP among the plurality of APs; determine, by the mobile device, AP vicinity information corresponding to the at least one AP based on the first group ID and the set of AP-specific information, the AP vicinity information indicating a plurality of locations relative to the at least one AP; and receive, at the mobile device, second assistance data corresponding to a second plurality of APs, wherein the second assistance data comprises a second group data that is common among the second plurality of APs, the second group data being associated with a second group ID, and the second plurality of APs comprising at least one of the APs in the plurality of APs, wherein the second group data comprises information corresponding to a second reference grid, wherein the second reference grid is used in determining the set of AP-specific information.
 8. The non-transitory computer-readable medium of claim 7, wherein the reference grid comprises at least one of a common grid point spacing, common grid origin, and a common grid orientation.
 9. The non-transitory computer-readable medium of claim 7, wherein the first group data further comprises at least one of a version and a validity period.
 10. A mobile device for obtaining assistance data corresponding to a plurality of access points (APs), comprising: means for receiving, at the mobile device, first assistance data from a location server, wherein the first assistance data comprises a first group data that is common among the plurality of APs, wherein the first group data is associated with a first group identifier (ID), the group ID, assigned to each AP of the plurality of APs, and wherein the first group data comprises information corresponding to a reference grid that is used in determining AP-specific information corresponding to each of the plurality of APs; means for receiving, at the mobile device, the first group ID and a set of AP-specific information for at least one AP among the plurality of APs; means for determining, by the mobile device, AP vicinity information corresponding to the at least one AP based on the first group ID and the set of AP-specific information, the AP vicinity information indicating a plurality of locations relative to the at least one AP; and means for receiving, at the mobile device, second assistance data corresponding to a second plurality of APs, wherein the second assistance data comprises a second group data that is common among the second plurality of APs, the second group data being associated with a second group ID, and the second plurality of APs comprising at least one of the APs in the plurality of APs, wherein the second group data comprises information corresponding to a second reference grid, wherein the second reference grid is used in determining the set of AP-specific information.
 11. The apparatus of claim 10, wherein the reference grid comprises at least one of a common grid point spacing, common grid origin, and a common grid orientation.
 12. The apparatus of claim 10, wherein the first group data further comprises at least one of a version and a validity period. 